System for managing mobile station international subscriber directory number storage

ABSTRACT

Systems, methods, and apparatuses may include a Billing System (BS) node, Charging System (CS) node, and a mediation node for managing Mobile Station International Subscriber Directory Numbers (MSISDN)s for a telecommunication network. The system may make an MSISDN available for reassignment immediately or shortly after (e.g., seconds, minutes, days, or weeks after) receiving a cancelation request associated with the MSISDN. For instance, upon receiving the cancelation request, the system may store a line identifier with an association to the MSISDN and/or an International Mobile Subscriber Identity (IMSI) in a line identifier database, and the system may delete the MSISDN/IMSI from a user account database. The system may receive a Telephone Account Procedure (TAP) Call Detail Record (CDR) associated with the MSISDN/IMSI after receiving the cancelation request. Accordingly, the system may use the line identifier stored in the line identifier database to generate a billing report corresponding to the TAP CDR.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a divisional application which claims priority to commonlyassigned, co-pending U.S. patent application Ser. No. 16/417,087, filedMay 20, 2019. Application Ser. No. 16/417,087 is fully incorporatedherein by reference.

BACKGROUND

Telecommunication service providers operating 3rd Generation PartnershipProgram (3GPP) networks often use multiple nodes to manage MobileStation International Subscriber Director Numbers (MSISDN)s (e.g., phonenumbers), to manage user accounts assigned to the MSISDNs, and togenerate billing reports for the user accounts based on phone callsassociated with the MSISDNs. The nodes must perform multiple operationsto accommodate different types of usage information originating fromdifferent service providers, for instance, via a Telephone AccountProcedure (TAP).

For instance, a TAP Call Detail Record (CDR) originating from a regionoutside the United States may arrive at a node in the United States ofthe service provider managing MSISDNs months after the network usagerepresented by the TAP CDR occurred. For example, a user with an MSISDNassigned to a user account with a U.S. carrier may make a phone callwhile traveling abroad. The phone call may be facilitated by a networkof a non-U.S. carrier operating in the country of the phone call. Asnoted above, the process for generating the TAP CDR for the phone calland delivering it to U.S. carrier responsible for billing the MSISDNassociated with the phone call may take months.

The user may cancel a phone plan or subscription associated with theuser account of the service provider (e.g., the U.S. carrier). However,because of the possibility of receiving delayed CDRs after canceling theuser account, the service provider node(s) typically stores the MSISDNwith the association to the user account for an additional period of,for instance, 60-90 days after receiving the cancelation request. Duringthis additional period, the MSISDN is unavailable to be reassigned to adifferent user account. Furthermore, in instances where the MSISDN isassociated with a post-paid plan, the node(s) must store charginginformation associated with the post-paid plan as well.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 depicts example systems, methods, and apparatuses for managingMobile Station International Subscriber Directory Number storage for atelecommunication network including at least a Billing System node, aCharging System node, and a mediation node.

FIG. 2 depicts a schematic diagram of an example Billing System node,and operations of the Billing System node, the Charging System node andthe mediation node, which may form at least a portion of a system ofFIG. 1.

FIG. 3 depicts a schematic diagram of an example Charging System node,and operations of the Charging System node, the Billing System node, andthe mediation node, which may form at least a portion of a system ofFIG. 1.

FIG. 4 depicts a schematic diagram of an example mediation node, andoperations of the mediation node, the Billing System node, and theCharging System node, which may form at least a portion of a system ofFIG. 1.

FIG. 5 depicts one or more example operations that may be performed bythe systems, methods, and apparatuses of FIG. 1, and may includetechniques for receiving a cancelation request and/or canceling anassociation of a Mobile Station International Subscriber DirectoryNumber with a user account.

FIG. 6 depicts one or more example operations that may be performed bythe systems, methods, and apparatuses of FIG. 1, and may includetechniques for generating a billing report based, at least in part, onreceiving a Telephone Account Procedure Call Detail Record.

DETAILED DESCRIPTION

Systems, methods, and apparatuses (hereinafter the “system”) disclosedherein may include a Billing System (BS) node, Charging System (CS)node, and a mediation node for managing Mobile Station InternationalSubscriber Directory Numbers (MSISDN)s for a telecommunication network.The BS node may perform operations for storing user account informationand generating billing reports. The CS node may perform operations forapplying a charging rate to usage information received in a Call DetailRecords (CDR)s to generate rated CDRs. The mediation node may performoperations for formatting CDRs received at the mediation node togenerate modified CDRs according to formatting requirements of the othernodes (e.g., the BS node or the CS node). The system disclosed hereinmay improve MSISDN management by making an MSISDN available forreassignment immediately or shortly after (e.g., minutes, days, or weeksafter) receiving a cancelation request associated with the MSISDN. Thesystem may shift memory and processing requirements of the BS node tothe CS node, improving the functioning of the BS node. For instance, thesystem may shift rate charging information (e.g., a charging rate) for apost-paid plan associated with the MSISDN to the CS node upon receivingthe cancelation request. In some instances, the BS node may shiftresponsibility for applying charging information to the CS node via anode alias (e.g., a line identifier).

In some examples, the BS node may store an MSISDN in a user accountdatabase with a first association to a user account. In some instances,the BS node may store the charging rate for the post-paid planassociated with the user account. Upon receiving a cancelation request,the BS node may store a line identifier at a BS node line identifierdatabase with a second association to the MSISDN and/or an InternationalMobile Subscriber Identity (IMSI). In some instances, multiple IMSI(s)may be associated with the MSISDN, and/or multiple MSISDN(s) may beassociated with the IMSI. The BS node may remove, from the user accountdatabase, the first association, the MSISDN, and/or the IMSI. In someinstances, the BS node may replace the MSISDN with the line identifierin the user account database associated with the user account. The BSnode line identifier database may comprise a separate database from theuser account database so that the MSISDN can be immediately deleted fromthe user account database upon being stored in the BS node lineidentifier database. Accordingly, the system may make the MSISDN, whichmay be a scarce resource in highly populated areas, available forreassignment without substantial delay, improving MSISDN management ofthe system. The BS node may store a cancelation timestamp associatedwith line identifier, the MSISDN, the IMSI and/or canceling the firstassociation. The BS node may send, to the CS node and/or the mediationnode, an adjustment message indicating the second association and/or thecancelation timestamp.

In some instances, the CS node, at least partly in response to receivingthe adjustment message, may store the line identifier in a rateinformation database. For instance, the CS node may replace, in the rateinformation database, the MSISDN with the line identifier, such that theline identifier is associated with a charging rate in the rateinformation database that was previously associated with the MSISDN. Thecharging rate may comprise a post-paid plan charging rate received fromthe adjustment message. The CS node may replace the MSISDN with the lineidentifier in the rate information database. Additionally, oralternatively, in some instances, the CS node may store an associationof the charging rate to the line identifier. In some embodiments, the CSnode may send, to the mediation node, an adjustment CDR indicating thesecond association of the MSISDN and/or the IMSI(s) associated with theline identifier and, in some instances, the cancelation timestamp.

In some embodiments, the mediation node may receive the adjustment CDRand store, at a mediation node line identifier database, the secondassociation of the MSISDN and/or the IMSI(s) associated with the lineidentifier. In some instances, the mediation node may store thecancelation timestamp with an association with the line identifier, theMSISDN, and/or the IMSI(s).

In some examples, the system may receive a Telephone Account Procedure(TAP) CDR. For instance, the mediation node may receive the TAP CDR froma third-party data clearing node. The TAP CDR may indicate usageinformation associated with the MSISDN and/or the IMSI(s) and a usagetimestamp. The mediation node may determine whether the usage timestampindicates a first time occurring prior to a second time indicated by thecancelation timestamp, and, if yes, may determine to send a modified TAPCDR to the CS node or the BS node indicating the line identifier (e.g.,instead of the MSISDN) and the usage information.

In some embodiments, the CS node may receive the modified TAP CDR and,based on the line identifier indicated by the modified TAP CDR,determine the charging rate stored in the rate information databaseassociated with the line identifier. The CS node may apply the chargingrate to the usage information to generate rated usage informationindicating a balance owed by a user associated with the user account.The CS node may generate and send a rated TAP CDR indicating the ratedusage information and the line identifier to the mediation node.

In some examples, the mediation node may receive the rated TAP CDR. Themediation node may determine that the BS node is a terminating node ofthe rated TAP CDR (e.g., intended recipient), and may apply formattingrules associated with the BS node to the rated TAP CDR, generating amodified rated TAP CDR. The modified rated TAP CDR may include, inaccordance with BS node formatting rules, an indication of the ratedusage information with an association to the line identifier. Themodified rated TAP CDR and/or the rated TAP CDR may omit the MSISDN. Themediation node may send the modified rated TAP CDR to the BS node. Insome examples, the mediation node may send a message, e.g., to anarchive node for legal and/or accounting recordation, indicating theusage information, the rated usage information, the MSISDN, the lineidentifier, the line identifier replaced with the MSISDN, the MSISDNreplaced with the line identifier, the association of the MSIDN and/orthe IMSI(s) with the line identifier, the usage timestamp, thecancelation timestamp, or combinations thereof.

The BS node may receive the modified rated TAP CDR. The BS node mayreceive the line identifier from the modified rated TAP CDR, anddetermine that the line identifier is associated with the MSISDN basedon the association of the line identifier with the MSISDN and/or theIMSI stored at the BS node line identifier database. Accordingly, the BSnode may generate, based on the line identifier received in the modifiedrated TAP CDR, a billing report for the user account, for instance, theuser account that was associated with the MSISDN prior to receiving thecancelation request. The BS node may send the billing report to alocation associated with the user account. A system including the BSnode, the CS node, the mediation node, and operations thereof arediscussed in greater detail below.

FIG. 1 depicts an example system 100 for managing MSISDN storage for atelecommunication network, such as a 3rd Generation Partnership Program(3GPP) network. For instance, the system 100 may manage MSISDN storagefor a 3G network, a 4G network, a 4G Long Term Evolution (LTE) network,a LTE Advanced network, a 5G network, an evolved IP Multimedia System(IMS) network, combinations thereof, and the like. The system 100 mayinclude a Billing System (BS) node 102, which may communicate with aCharging System (CS) node 104 and/or a mediation node 106.

In some examples, the BS node 102 may generate and/or send billingreports based on MSISDNs associated with user accounts (e.g., stored ata user account database 108) and/or one based on or more Call DetailRecords (CDR)s received at the BS node 102 (e.g., modified CDRs receivedfrom the mediation node 106). A CDR of the one or more CDRs may comprisea data record produced, for instance by a telephone exchange or othertelecommunications equipment of a service provider. The CDR may documentdetails of a telephone call or other telecommunications transaction(e.g., Short Message Service (SMS) message) that passes through theequipment. In some examples, the CDR may originate from a TelephoneApplication Server (TAS) node 110. The BS node 102 may comprise arecord-keeping archive of received CDRs and/or generated billingreport(s). The BS node 102 may include a BS node line identifierdatabase 112 for storing line identifiers associated with MSISDNs 206and/or one or more IMSI(s) 207.

In some embodiments, the CS node 104 may store one or more MSISDN(s)associated with corresponding charging rate(s) that reflect paymentplans and/or billing rates for the MSISDNs (e.g., to apply to usageinformation associated with the MSISDN). The CS node 104 may generaterated CDRs based on CDRs received at the CS node 104 (e.g., unrated CDRsreceived from the mediation node 106 and/or from the TAS node 110). Uponreceiving a CDR indicating usage information associated with aparticular MSISDN, the CS node may determine a particular charging ratecorresponding to the particular MSISDN (e.g., by matching an MSISDNindicated by the CDR with an MSISDN stored in a rate informationdatabase 114). The CS node may apply the charging rate to the usageinformation in order to generate a rated CDR, e.g., a CDR indicating abalance of debt owed by the user account associated with MSISDN.

In some examples, the mediation node 106 may generate modified (e.g.,formatted) CDRs, for instance, based on CDR (e.g., rated or unratedCDRs) received at the mediation node 106. For instance, a CDR 116 may besent from the TAS node 110 to the CS node 104. The CS node 104 may applythe charging rate to the CDR 116 to generate a rated CDR, which the CSnode may send to the mediation node 106. The mediation 106 node maymodify the rated CDR received from the CS node 104 to match formattingrequirements of the BS node 102, and generate a modified rated CDR tosend to the BS node 102.

In some embodiments, the system 100 may comprise a third-party dataclearing node 118. The third-party data clearing node 118 may receiveone or more Transferred Account Procedure (TAP) CDR(s) 120, forinstance, from an international service provider and/or from athird-party service provider that is different from the service provideroperating the BS node 102, the CS node 104, and/or the mediation node106. The third-party data clearing node 118 may send the TAP CDR(s) 120to the mediation node 106.

FIG. 2 depicts a schematic diagram of an example system 200 including atleast the BS node 102. FIG. 2 depicts one or more components of the BSnode 102, one or more operations performed by the BS node 102, and oneor more messages, CDRs, and other data transmissions between the BS node102 and other nodes (e.g., the CS node 104 and the mediation node 106)of the system 100.

In some instances, the BS node 102 may comprise one or morecomputer-readable storage media 202, such as non-transitorycomputer-readable media including, but not limited to, phase changememory (PCM), static random-access memory (SRAM), dynamic random-accessmemory (DRAM), other types of random access memory (RAM), read onlymemory (ROM), electrically erasable programmable ROM (EEPROM), flashmemory or other memory technology, compact disc ROM (CD-ROM), digitalversatile discs (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,a quantum-state storage device, genetic encoding storage device,combinations thereof, or any other medium that can be used to storeinformation for access by an electronic computing device. Databasesdiscussed herein, for instance stored at computer-readable storage media202, may include one or more of a comma delimited list, a spreadsheet,an array, a NoSQL data structure, a hash-based data structure, anobject-based data structure, or any other data type, data structure,and/or data system for storing retrievable data.

In some examples, The BS node 102 may comprise one or more processor(s)204, such as a microprocessor, a microcomputer, a microcontroller, adigital signal processor, a central processing unit (CPU), a graphicsprocessing unit (GPU), a quantum processor, combinations thereof, etc.Among other capabilities, the one or more processor(s) 204 may operateto fetch and execute computer-readable instructions stored in the one ormore memory storage device(s) 202, for instance, to perform theoperations disclosed herein.

In some examples, the BS node 102 may store, for instance atcomputer-readable storage media 202, the user account database 108,which may store associations of one or more MSISDN(s) 206 with one ormore user account(s) 208. The BS node may comprise an archive of billinginformation corresponding with a user that opened the user account 208,such as an archive of CDRs (and information represented by the CDRs)associated with the user account 208, billing reports generated and/orsent by the BS node 102 associated with the user account 208, personalinformation (e.g., name, billing address, phone number, etc.) associatedwith the user account, etc. In some embodiments, the user accountdatabase 108 may comprise a permanent (or long term) record of billinginformation associated with the user account 208.

In some examples, the BS node 102 may comprise the BS node lineidentifier database 112. For instance, the BS node line identifierdatabase 112 may store, at the BS node 102 and/or in communication withthe processor(s) 204 of the BS node 102, one or more firstassociation(s) 210 of the MSISDN(s) 206 and/or the IMSI(s) 207 with oneor more line identifier(s) 212. In some examples, in response toreceiving a cancelation request 214, the BS node 102 may generate theline identifier 212, for instance, via a line identifier generator 216.The line identifier generator 216 may generate the line identifier 212to comprise an alphanumeric string, which may satisfy a formattingrequirement of the BS node line identifier database 112. In someinstances, the format of the line identifier 212 may be different from aformat of the MSISDN 206, for example, the line identifier 212 maycomprise less digits or bits than the MSISDN 206. In some examples, theBS node 102 may receive the line identifier 212, for instance, fromanother line identifier generator separate from the BS node 102. In someexamples, the BS node 102 may receive and/or generate the lineidentifier 212 in response to receiving an indication that anassociation of a particular MSISDN to a particular user account is nolonger accurate or available.

In some examples, the cancelation request 214 may include a cancelationtimestamp 218, for instance, indicating a time associated with acancelation of the user account 208 and/or a cancelation of a secondassociation 220 of the MSISDN 206 with the user account 208. In someembodiments, the BS node 102 may generate the cancelation timestamp 218at least partly in response to receiving the cancelation request 214.Additionally, or alternatively, the cancelation request 214 may includethe cancelation timestamp 218 prior to the BS node 102 receiving thecancelation request 214. The BS node 102 may store the cancelationtimestamp 218, for instance, in the BS node line identifier database 112and/or in the user account database 108. The cancelation timestamp 218may be stored with an association to the line identifier 212, the MSISDN206, the IMSI(s) 207, and/or the user account 208.

In some examples, the BS node 102 may comprise a CS node adjustmentgenerator 222, for instance, stored in the computer-readable storagemedia 202. The CS node adjustment generator 222 may generate adjustmentmessage(s) 224 to send to the CS node 104, for instance, based at leastin part on receiving the cancelation request 214, generating the lineidentifier 212, and/or storing the first association 210. The adjustmentmessage 224 may include data representing the first association 210 ofthe MSISDN 206 and/or the IMSI(s) 207 with the line identifier 212. Theadjustment message 224 may include a charging rate which may comprisepayment plans and/or billing rates associated with the MSISDN 206. Insome instance, the charging rate may comprise a post-paid plan chargingrate of the user account 208. The adjustment message 224 may include aninstruction to store the association 210, the MSISDN 206, the lineidentifier 212, and/or the charging rate at the CS node 104, asdiscussed in greater detail below regarding FIGS. 3 and 5.

In some instances, the BS node 102 may comprise a billing reportgenerator 226 (e.g., stored in the computer-readable media 202) togenerate a billing report 228. In some examples, the BS node 102 (e.g.,via the billing report generator 226) may receive rated usageinformation (e.g., indicating a balance of an owed amount associatedwith user account 208), for instance, included in a modified rated TAPCDR 230 sent to the BS node 102 from the mediation node 106. Themodified rated TAP CDR 230 may be based, at least in part, on the TAPCDR 120. The modified rated TAP CDR 230 is discussed in greater detailbelow regarding FIG. 4. The billing report generator 226 may apply billgenerating techniques, such as for generating emails and/or snail maildocuments, to generate the billing report 228. The billing report 228may include the usage information, the rated usage information, thebalance, and/or a location associated with the user account 208. The BSnode 102 may send the billing report 228 to the location.

FIG. 3 depicts a schematic diagram of an example system 300 including atleast the CS node 104. FIG. 3 depicts one or more components of the CSnode 104, one or more operations performed by the CS node 104, and oneor more messages, CDRs, or other data transmissions between the CS node104 and other nodes (e.g., the BS node 102 and the mediation node 106)of the system 100.

In some examples, the CS node 104 may comprise one or morecomputer-readable storage media 302, such as non-transitorycomputer-readable media including, but not limited to, phase changememory (PCM), static random-access memory (SRAM), dynamic random-accessmemory (DRAM), other types of random access memory (RAM), read onlymemory (ROM), electrically erasable programmable ROM (EEPROM), flashmemory or other memory technology, compact disc ROM (CD-ROM), digitalversatile discs (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,a quantum-state storage device, genetic encoding storage device,combinations thereof, or any other medium that can be used to storeinformation for access by an electronic computing device. Databasesdiscussed herein, for instance stored at computer-readable storage media302, may include one or more of a comma delimited list, a spreadsheet,an array, a NoSQL data structure, a hash-based data structure, anobject-based data structure, or any other data type, data structure,and/or data system for storing retrievable data.

In some embodiments, the CS node 104 may comprise one or moreprocessor(s) 304 such as a microprocessor, a microcomputer, amicrocontroller, a digital signal processor, a central processing unit(CPU), a graphics processing unit (GPU), a quantum processor,combinations thereof, etc. Among other capabilities, the one or moreprocessor(s) 304 may operate to fetch and execute computer-readableinstructions stored in the one or more memory storage media 302 toperform the operations disclosed herein.

In some examples, the CS node 104 may store the rate informationdatabase 114 at computer-readable storage media 302. The rateinformation database 114 may store charging rate(s), for instance, afirst charging rate 306(A) associated with the user account 208, forinstance via a first association 308(A) with the MSISDN 206. The firstcharging rate 306(A) may represent a contractual obligation that a userassociated with the user account 208 will be charged a particular ratefor a particular usage, such as about $0.25 per minute for internationalcalls, about $0.10 per international text message (e.g., SMS message),about $1.00 per megabyte (MB) of data for domestic roaming (e.g., over athreshold free amount of, for instance, 1 gigabyte), about $15 per MB ofdata for international roaming, or combinations thereof. In someinstances the first charging rate 306(A) may be associated with aprepaid plan (such that a user pays upfront and rated usage amounts arededucted from the prepaid balance) or a post-paid plan (such that theuser is charged at the end of a month so that charges may accumulatethroughout the month). The first charging rate 306(A) may includeparticular associations of rates for particular regions, times of day,devices, high-traffic or low-traffic periods, or combinations thereof.For instance, the CS node 104 may store the first charging rate 306(A)for a first region (e.g., the U.S.) which may be different than anothercharging rate for a second region (e.g., the E.U.).

In some embodiments, the CS node 104 may receive the adjustment message224, for instance, from the BS node 102. The CS node 104 may remove,cancel, delete, omit, or otherwise change the first association 308(A)of the first charging rate 306(A) with the MSISDN 206. The CS node 104may generate and store a second association 308(B) of the lineidentifier 212 with the first charging rate 306(A) and, in someinstances, may delete the first association 308(A) and/or rewrite over amemory location storing the first association 308(A) with the secondassociation 308(B). The CS node 104 may rewrite over a memory locationstoring the MSISDN 206 with the line identifier 212. In some examples,the CS node 104 may store a third association 308(C) of a secondcharging rate 306(B) associated with the MSISDN 206, for instance, afterdeleting the first association 308(A).

In some examples, the CS node 104 may send, via a mediation nodeadjustment generator 310, an adjustment CDR 312, for instance, based atleast in part on receiving the adjustment message 224, storing the lineidentifier 212, and/or storing the second association 308(B). Theadjustment CDR 312 may include data representing the first association210 of the MSISDN 206 and/or the IMSI(s) 207 associated with the lineidentifier 212, and/or the cancelation timestamp 218. The adjustment CDR312 may include an instruction to store the first association 210, the,the MSISDN 206, the IMSI(s) 207, the line identifier 212, and/or thecancelation timestamp 218 at the mediation node 106, as discussed ingreater detail below regarding FIGS. 4 and 5.

In some embodiments, the CS node 104 may receive a CDR, such as amodified TAP CDR 314 from the mediation node 106. One or more CDR(s)received at the CS node 104 may comprise unrated CDR(s). The modifiedTAP CDR 314 received at the CS node 104 may be associated with apre-paid plan or a post-paid plan. Upon receiving the modified TAP CDR314, a CDR rating generator 316 may apply a charging rate, for instance,first charging rate 306(A) associated with the line identifier 212, tousage information 318 represented by the unrated TAP CDR 314.Accordingly, the CS node 104 may generate a rated TAP CDR 320 from themodified TAP CDR 314. The CS node 104 may send the rated TAP CDR 320 tothe mediation node 106. The rated TAP CDR 320 may include an instructionto the mediation node 106 to format the rated TAP CDR 320, for instance,according to formatting requirements of the BS node 102, and to send aproperly formatted rated TAP CDR 320 (e.g., a modified rated TAP CDR) tothe billing node 102. In some examples, the CS node 104 may apply thecharging rate associated with a post-paid plan (e.g., the charging ratereceived from the BS node 102 in the adjustment message 224) to themodified TAP CDR 314 in order to generate the rated TAP CDR 320.Accordingly, the rated TAP CDR 320 may be generated for the post-paidplan at the CS node 104 instead of at the BS node 102, such thatcomputing resources of the BS node 102 may be conserved and/or allocatedto other uses. Reducing rate charging performed at the BS node 102 mayreduce memory storage requirements of the computer-readable media 202 ofthe BS node 102 because the BS node 102 does not need to store the logicto perform rate charging for post-paid plans. Therefore,eliminating/reducing a process for rating TAP CDRs 120 or modified TAPCDRs 314 for post-paid plans at the BS node 102 improves the overallefficiency of the systems disclosed herein.

FIG. 4 depicts a schematic diagram of an example system 400 including atleast the mediation node 106. FIG. 4 depicts one or more components ofthe mediation node 106, one or more operations performed by themediation node 106, and one or more messages, CDRs, or other datatransmissions between the mediation node 106 and other nodes (e.g., theBS node 102 and the CS node 104) of the system 100.

In some examples, the mediation node 106 may comprise one or morecomputer-readable storage media 402 such as non-transitorycomputer-readable media including, but not limited to, phase changememory (PCM), static random-access memory (SRAM), dynamic random-accessmemory (DRAM), other types of random access memory (RAM), read onlymemory (ROM), electrically erasable programmable ROM (EEPROM), flashmemory or other memory technology, compact disc ROM (CD-ROM), digitalversatile discs (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,a quantum-state storage device, genetic encoding storage device,combinations thereof, or any other medium that can be used to storeinformation for access by an electronic computing device. Databasesdiscussed herein, for instance stored at computer-readable storage media402, may include one or more of a comma delimited list, a spreadsheet,an array, a NoSQL data structure, a hash-based data structure, anobject-based data structure, or any other data type, data structure,and/or data system for storing retrievable data.

In some embodiments, the mediation node 106 may comprise one or moreprocessor(s) 404 such as a microprocessor, a microcomputer, amicrocontroller, a digital signal processor, a central processing unit(CPU), a graphics processing unit (GPU), a quantum processor,combinations thereof, etc. Among other capabilities, the one or moreprocessor(s) 404 may operate to fetch and execute computer-readableinstructions stored in the one or more memory storage media 402 toperform the operations disclosed herein.

In some examples, the mediation node 106 may store a mediation node lineidentifier database 406, for instance, in the computer-readable storagemedia 402. The mediation node line identifier database 406 may store, atthe mediation node 106 and/or in communication with the processor(s) 404of the mediation node 106, one or more association(s) 408 of theMSISDN(s) 206 and/or the IMSI(s) 207 with one or more line identifier(s)212, in some examples, in response to receiving the adjustment CDR 312.The mediation node 106 may store the cancelation timestamp 218 (whichmay be included in the adjustment CDR 312), for instance, at themediation node line identifier database 406 and associated with the lineidentifier 212, the MSISDN 206, and/or the IMSI(s) 207.

In some embodiments, the mediation node 106 may store a CDR formatter410, for instance, in the computer-readable storage media 402. The CDRformatter 410 may receive CDRs sent to the mediation node 106 (e.g.,from the CS node 104, from the TAS node 110, and/or from the third-partydata clearing node 118) and may apply stored CDR formats stored in a CDRformat database in order to generate modified CDRs. For instance, theCDR formatter 410 may recognize an identity of a terminating nodeaddress associated with a received CDR (e.g., an intended recipientidentifier), and the mediation node 106 may determine a formatassociated with the terminating node address, which may correspond tothe BS node 102.

In some examples, the mediation node 106 may receive the TAP CDR 120,for instance, from the third-party data clearing node 118. The TAP CDR120 may include usage information 318 corresponding to a usage (e.g., aphone call, a text, a data usage, roaming, etc. associated with theMSISDN 206 and/or the IMSI(s) 207), which may be collected by athird-party service provider, for instance, in a region outside the U.S.The TAP CDR 120 may include an indication of a location where the usageoccurred, a usage timestamp 412 associated with the usage information318, the MSISDN 206 and/or the IMSI(s) 207, and/or an association 414 ofthe MSISDN 206 and/or the IMSI(s) 207 with the usage information 318.

In some instances, the mediation node 106 may determine a receipttimestamp of the TAP CDR 120 representing a time that the mediation node106 receives the TAP CDR 120, which (by way of example) may be up to60-90 days later than a time indicated by the usage timestamp 412because the mediation node 106 may receive the TAP CDR 120 a substantialdelay after the usage occurred.

In some examples, upon receiving the TAP CDR 120, the mediation node 106may determine whether the usage timestamp 412 indicates a first timeoccurring prior to or after a second time indicated by the cancelationtimestamp 218. For instance, the mediation node 106, in some examples,via a timestamp assessor 415 (e.g., stored at the computer-readablemedia 402), may identify the usage timestamp 412 and the MSISDN 206and/or the IMSI(s) 207 from the TAP CDR 120, determine that the MSISDN206 and/or the IMSI(s) 207 corresponds to the cancelation timestamp 218and/or the line identifier 212, and/or determine which of the first timeor the second time occurred earlier.

In some instances, upon making a determination that the first timeindicated by the usage timestamp 412 occurred before the second timeindicated by the cancelation timestamp 218, the mediation node 106(e.g., via the timestamp assessor 415) may determine to generate amodified TAP CDR 416 (which may be similar or identical to modified TAPCDR 314). For instance, the mediation node 106 may duplicate informationof the TAP CDR 120 into the modified TAP CDR 416. The mediation node 106may receive the line identifier 212 and/or the association 408 from themediation node line identifier database 406, and the mediation node 106may replace the MSISDN 206 and/or the IMSI(s) 207 in the TAP CDR 120with the line identifier 212 to create the modified TAP CDR 416. Inother words, the CDR formatter 410 may generate the modified TAP CDR 416to include the line identifier 212 and omit the MSISDN 206. In someexamples, the mediation node 106 may send the modified TAP CDR 416 tothe CS node 104. The modified TAP CDR 416 may be associated with apost-paid plan.

In some embodiments, the mediation node 106 may receive the rated TAPCDR 320 from the CS node 104. The rated TAP CDR 320 may include ratedusage information 418 representing a balance owed associated with theuser account 208, which may be based at least in part on applying thecharging rate 306(A) to the usage information 318 at the CS node 104.The mediation node 106 may apply formatting rules, for instance, via theCDR formatter 410, to the rated TAP CDR 320 to generate a modified ratedTAP CDR 420 from the rated TAP CDR 320. For instance, the CDR formatter410 may format the modified rated TAP CDR 420 according to formattingrules associated with the BS node 102. The mediation node 106 may sendthe modified rated TAP CDR 420 to the BS node 102. The modified ratedTAP CDR 420 may include the rated usage information 418 and the lineidentifier 212. The modified rated TAP CDR 420 may omit the MSISDN 206and/or include an absence of the MSISDN 206.

In some examples, components of the BS node 102 (e.g., processor 204,computer-readable storage media 202, etc.), the CS node 104 (e.g.,processor 304, computer-readable storage media 304, etc.), and/or themediation node 106 (e.g., processor 404, computer-readable storage media402, etc.) may be stored separately as separate physical nodes, e.g., aphysical distance apart. In some instances, components of the BS node102, the CS node 104, and/or the mediation node 106 may at be at leastpartially combined, and/or entirely combined to form various nodecombinations.

FIG. 5 depicts an example process of system 500 including techniques forcanceling an MSISDN association based, at least in part on receiving thecancelation request 214. The techniques depicted in FIG. 5 may includeadjusting the BS node 102, the CS node 104, and/or the mediation node106 based, at least in part, on receiving the cancelation request 214.The system 500 depicted in FIG. 5 may be similar to, identical to,and/or form a portion of any of the systems disclosed herein.

At step 502, the process may include receiving a cancelation requestassociated with a MSISDN stored in a user account database. Forinstance, the BS node 102 may receive the cancelation request 214associated with the MSISDN 206 stored at the user account database 108.The cancelation request 214 may include the MSISDN 206 and an indication(e.g., an instruction) that the BS node 102 remove, e.g., from thecomputer-readable media 202, the second association 220 of the MSISDN206 associated with the user account 208, for instance, based on a userassociated with the user account 208 performing a cancelation action forthe user account 208. The cancelation request 214 may include thecancelation timestamp 218, for instance, indicating the time associatedwith the cancelation action of the user account 208 and/or a cancelationof the second association 220. In some instances, the BS node 102 maygenerate the cancelation timestamp 218 at least partly in response toreceiving the cancelation request 214.

At step 504, the process may include storing a line identifier with afirst association of the line identifier associated with the MSISDNand/or the IMSI(s) 207. For instance, the BS node 102 may store the lineidentifier 212 at the BS node line identifier database 112 with thefirst association 210 of the line identifier 212 associated with theMSISDN 206 and/or the IMSI(s) 207. For example, based in part onreceiving the cancelation request 214 the BS node line identifierdatabase 112 may store, at the BS node 102 and/or in communication withthe processor(s) 204 of the BS node 102, one or more firstassociation(s) 210 of the MSISDN(s) 206 and/or the IMSI(s) 207 with oneor more line identifier(s) 212, based, at least in part, on receivingthe cancelation request 214. In some examples, in response to receivingthe cancelation request 214, the BS node 102 may generate the lineidentifier 212, for instance, via the line identifier generator 216. Theline identifier generator 216 may generate the line identifier 212 tocomprise an alphanumeric string, which may satisfy formattingrequirements of the BS node line identifier database 112.

At step 506, the process may include deleting a second association ofthe MSISDN associated with a user account. For instance, the BS node 102may delete, from the user account database 108, the first association210 of the MSISDN 206 associated with a first user account. Forinstance, the BS node 102 may remove, cancel, delete, omit, or otherwisechange the first association 210. Upon performing step 506, the MSISDN206 may be available for reassignment, for instance, to a second useraccount. In some instances, the BS node 102 may delete the firstassociation 210 within seconds, minutes, one day, one week, and/or lessthan thirty days after receiving the cancelation request 214 such thatthe MSISDN is immediately or shortly thereafter available forreassignment to the second user account.

At step 508, the process may include storing a third association of theMSISDN associated with a second user account. For instance, the BS node102 may store, in the user account database 108, the third associationof the MSISDN 206 associated with the second user account. For instance,the BS node 102 may receive an indication that a second user associatedwith the second user account has purchased a subscription and/or atelephone service plan that includes an assignment of the MSISDN 206 tothe second user, e.g., via the third association of the MSISDN 206 tothe second user account in the user account database 108. In someexamples, the BS node 102 may generate the third association of theMSISDN 206 associated with the second user account within seconds,minutes, one day, one week, and/or less than thirty days after receivingthe cancelation request 214. Accordingly, the system 500 may efficientlymanage the MSISDNs by reassigning MSISDNs quickly after receiving thecancelation request 214, and without needing to store unused/canceledMSISDNs for an extended time period after receiving the cancelationrequest 214. In some instances, the MSISDNs may comprise a scarceresource, such as in high-density population areas, and so quicklyreassigning MSISDNs may expand a number of users that can receive MSISDNassignments from the service provider managing the MSISDNs.

At step 510, the process may include receiving a first messageindicating the first association and storing the line identifier and afourth association of the line identifier associated with a firstcharging rate. For instance, the CS node 104 may receive the firstmessage indicating the first association 210 and store, at the rateinformation database 114, the line identifier 212. The CS node 104 mayreceive the adjustment message 224, for instance, from the BS node 102.The CS node 104 may remove, cancel, delete, omit, or otherwise changethe first association 308(A) of the first charging rate 306(A) with theMSISDN 206, rewriting over a memory location that stored the firstassociation 308(A) with the fourth association, and/or rewriting over amemory location that stored the MSISDN 206 and/or the IMSI(s) 207 withthe line identifier 212.

At step 512, process may include storing a fifth association of theMSISDN associated with a second charging rate corresponding to thesecond user account. For instance, the CS node 104 may store, at therate information database 114 the fifth association of the MSISDN 206associated with the second charging rate corresponding to the seconduser account. For instance, the fifth association may comprise the thirdassociation 308(C) depicted in FIG. 3, and the second charging rate maycomprise second charging rate 306(B). For instance, the CS node 104 mayreceive an indication from the BS node 102 that the second userassociated with the second user account purchased a subscription, atelephone service plan, or otherwise initiated an assignment of theMSISDN 206 to the second user account. In some examples, the CS node 104may generate the fifth association of the MSISDN 206 associated with thesecond charging rate within seconds, minutes, one day, one week, and/orless than thirty days after the BS node 102 receives the cancelationrequest 214, and/or after receiving the indication from the BS node.

At step 514, the process may include receiving an adjustment CDRindicating the first association and storing the first association and atimestamp. For instance, the mediation node 106 may receive theadjustment CDR 312 indicating the first association 210 of the lineidentifier 212 with the MSISDN 206 and/or the IMSI(s) 207, and store, atthe mediation node line identifier database 406, the first association210 with the cancelation timestamp 218. The adjustment CDR 312 may begenerated and/or sent from the CS node 104 to the mediation node 106. Insome examples, the CS node 104 may send, via the mediation nodeadjustment generator 310, the adjustment CDR 312, for instance, based atleast in part on receiving the adjustment message 224 at the CS node104, storing the line identifier 212 at the CS node 104, and/or storingthe association 308(B) at the CS node 104. The adjustment CDR 312 mayinclude data representing the first association 210 of the MSISDN 206and/or the IMSI(s) 207 associated with the line identifier 212. Theadjustment CDR 312 may include an instruction to store the firstassociation 210, the MSISDN 206 and/or the IMSI(s) 207, the lineidentifier 212, and/or the cancelation timestamp 218 at the mediationnode 106

In some instances, the mediation node 106 may store, at the mediationnode line identifier database 406, the first association 210, the MSISDN206 and/or the IMSI(s) 207, and/or the cancelation timestamp 218. Forinstance, the first association 210 of the line identifier 212associated with the MSISDN 206 may be stored based, at least in part, onthe mediation node 106 receiving the adjustment CDR 312. In someexamples, the mediation node 106 may store the first association 210with the cancelation timestamp 218, for instance, indicating the timeassociated with a cancelation of the user account 208 and/or acancelation of the second association 220 of the MSISDN 206 with theuser account 208. In some embodiments, the BS node 102 may generate thecancelation timestamp 218 at least partly in response to receiving thecancelation request 214. In some examples, the CS node 104 may generatethe cancelation timestamp 218, for instance, at least partly in responseto receiving the adjustment message 224. In some embodiments, themediation node 106 may generate the cancelation timestamp 218, forinstance, at least partly in response to receiving the adjustment CDR312. In some instances, any of the steps 502-514 may be performed atleast partly in response to any other of the steps 502-514, such as atleast partly in response to the system receiving the cancelation request214.

FIG. 6 depicts an example process of system 600 including techniques forgenerating the billing report 228. In some instances, the billing report228 may be generated by the BS node 102 based, at least in part onreceiving (e.g., at the mediation node 106) the TAP CDR 120. The system600 depicted in FIG. 6 may be similar to, identical to, and/or form aportion of any of the systems disclosed herein.

At step 602, the process may include receiving a TAP CDR indicatingusage information associated with a MSISDN and/or an IMSI and a usagetimestamp. For instance, the mediation node 106 may receive the TAP CDR120 indicating the usage information 318 associated with the MSISDN 206and/or the IMSI(s) 207 and the usage timestamp 412. The TAP CDR 120 maybe sent to the mediation node 106 from the third-party data clearingnode 118. The TAP CDR 120 may include the usage information 318, whichmay be collected by a third-party service provider, for instance, in aregion outside the U.S. The TAP CDR 120 may include an indication of thelocation where the usage (e.g., phone call, text, data usage, roaming,etc. associated with the MSISDN 206) occurred, the usage timestamp 412associated with the usage information 318, and/or the association 414 ofthe MSISDN 206 and/or the IMSI(s) 207 with the usage information 318.

At step 604, the process may include determining that the usagetimestamp indicates a time prior to a cancelation request associatedwith a first association. For instance, the mediation node 106 maydetermine that the usage timestamp 412 indicates a first time occurringprior to a second time indicated by the cancelation timestamp 218, whichmay be associated with the first association 210 and/or the lineidentifier 212. For instance, the mediation node 106, in some examples,via the timestamp assessor 415 (e.g., stored at the computer-readablemedia 402), may identify the usage timestamp 412 and the MSISDN 206and/or the IMSI(s) 207 from the TAP CDR 120, determine that the MSISDN206 and/or the IMSI(s) 207 corresponds to the cancelation timestamp 218and/or the line identifier 212, and determine which of the first time orthe second time occurred earlier.

At step 606, the process may include generating and/or sending amodified TAP CDR. For instance, the mediation node 106 may generate themodified TAP CDR 416 and send the modified TAP CDR 416 to the CS node104. The modified TAP CDR 416 may include the line identifier 212 with asecond association to the usage information 318. For instance,generating the modified TAP CDR 416 may be based, at least in part onthe determination that the usage timestamp 412 indicates the first timeoccurring prior to the second time indicated by the cancelationtimestamp 218. The mediation node 106 may duplicate information of theTAP CDR 120 into the modified TAP CDR 416. The mediation node 106 mayreceive the line identifier 212 and/or the association 408 from themediation node line identifier database 406, and the mediation node 106may replace the MSISDN 206 and/or the IMSI(s) 207 with the lineidentifier 212 in the modified TAP CDR 416. In other words, the CDRformatter 410 of the mediation node 106 may generate the modified TAPCDR 416 to include the line identifier 212 and omit the MSISDN 206and/or the IMSI(s) 207. The CS node 104 may receive the modified TAP CDR416.

At step 608, process may include generating and/or sending a rated TAPCDR. For instance, the CS node 104 may generate the rated TAP CDR 320and send the rated TAP CDR 320 to the mediation node 106. The rated TAPCDR 320 may be generated based, at least in part, on the charging rateassociated the line identifier 212 and stored at the rate informationdatabase 114. For instance, the CDR rating generator 316 (which may bestored at computer-readable media 302 of the CS node 104) may apply thecharging rate 306 to the usage information 318 represented by themodified TAP CDR 416 in order to generate the rated TAP CDR 320. Therated TAP CDR 320 may include an instruction to the mediation node 106to format the rated TAP CDR 320, for instance, according to formattingrequirements of the BS node 102, and to send a properly formatted ratedTAP CDR 320 (i.e., the modified rated TAP CDR 420) to the billing node102. The mediation node 106 may receive the rated TAP CDR 320.

At step 610, process may include generating and/or sending a modifiedrated TAP CDR. For instance, the mediation node 106 may generate themodified rated TAP CDR 420 and send the modified rated TAP CDR 420 tothe BS node 102. In some instances, the modified rated TAP CDR 420 maybe based, at least in part, on the rated TAP CDR 320. For instance, themodified rated TAP CDR 420 may include the balance associated with theusage information 318 of the TAP CDR 120 (e.g., generated by the CS node104 applying the charging rate to the usage information 318), which maybe formatted by the mediation node 106. The mediation node 106 may applyformatting rules, for instance, via the CDR formatter 410 to the ratedTAP CDR 320, generating the modified rated TAP CDR 420. For instance,the CDR formatter 410 may format the modified rated TAP CDR 420according to formatting rules associated with the BS node 102. Themodified rated TAP CDR 420 may include the line identifier 212associated with the rated usage information and/or the balance. The BSnode 12 may receive the modified rated TAP CDR 420

At step 612, process may include generating and/or sending a billingreport to a location associated with a user account. For instance, theBS node 102 may generate the billing report 228. Generating the billingreport 228 may be based, at least in part, on receiving the lineidentifier 212 included in the modified rated TAP CDR 420, the ratedusage information in the modified rated TAP CDR 420, the balancegenerated by the CS node 104, and/or the first association 210 (storedat the BS node line identifier database 112) associating the lineidentifier 212 with the MSISDN 206. The BS node 102 may send the billingreport 228. For instance, the BS node 102 may send the billing report228 as an invoice to the user associated with the user account. In someexamples, the BS node 102 may send the billing report 228 to an archivefor storage for legal documentation and/or accounting purposes. In someinstances, any of the steps 602-612 may be performed at least partly inresponse to any other of the steps 602-612, such as at least partly inresponse to receiving the TAP CDR 120.

Although FIGS. 5 and 6 illustrate example operations, the describedoperations in these figures (and all other methods and operationsdisclosed herein) may be performed in other orders different than thoseillustrated in FIGS. 5 and 6 and multiple steps may be performedsimultaneously or in parallel. Furthermore, in some embodiments, one ormore operations illustrated in FIGS. 5 and 6 may be omitted, repeated,and/or combined with other operations illustrated in FIGS. 5 and 6, orany other operations and components discussed in this disclosure. Insome instances, the operations illustrated in FIGS. 5 and 6 may beperformed in multiple iterations for instance, to manage thousands, oreven millions of MSISDNs, user accounts, and/or cancelation requestsoccurring around the globe.

CONCLUSION

Although this disclosure uses language specific to structural featuresand/or methodological acts, it is to be understood that the scope of thedisclosure is not necessarily limited to the specific features or actsdescribed. Rather, the specific features and acts are disclosed asillustrative forms of implementation.

What is claimed is:
 1. A computing device comprising: one or moreprocessors; and one or more non-transitory computer-readable mediastoring computer-executable instructions that, when executed, cause theone or more processors to perform operations comprising: storing, in afirst database, i) a Mobile Station International Subscriber DirectoryNumber (MSISDN) or an International Mobile Subscriber Identity (IMSI)and ii) a first association of the MSISDN or the IMSI with a first useraccount; receiving a cancelation request associated with the MSISDN orthe IMSI; storing a second association of the MSISDN or the IMSI with aline identifier in a second database; removing the first association orthe MSISDN from the first database; storing the MSISDN and a thirdassociation of the MSISDN with a second user account in the firstdatabase; receiving a Call Detail Record (CDR) indicating the lineidentifier; and generating, based at least in part the secondassociation and receiving the CDR, a billing report associated with thefirst user account.
 2. The computing device of claim 1, wherein thethird association is stored less than one day after receiving thecancelation request.
 3. The computing device of claim 1, wherein the CDRis received from a mediation node storing an association between theline identifier and the MSISDN or the IMSI.
 4. The computing device ofclaim 1, wherein the operations further comprise storing a timestampassociated with the cancelation request representing an occurrence of auser account termination event, and wherein generating the billingreport is based, at least in part, on the timestamp.
 5. The computingdevice of claim 1, wherein: the CDR indicates usage informationassociated with the line identifier, the operations further comprisestoring a timestamp associated with the usage information, andgenerating the billing report is based, at least in part, on thetimestamp.
 6. The computing device of claim 1, wherein the operationsfurther comprise: storing a first timestamp associated with thecancelation request; storing a second timestamp associated with the CDR;and determining that the second timestamp indicates an earlier time thanthe first timestamp.
 7. The computing device of claim 1, wherein thecomputing device comprises a Billing System node.
 8. A methodcomprising: storing, in a first database, i) a Mobile StationInternational Subscriber Directory Number (MSISDN) or an InternationalMobile Subscriber Identity (IMSI) and ii) a first association of theMSISDN or the IMSI with a first user account; receiving a cancelationrequest associated with the MSISDN or the IMSI; storing a secondassociation of the MSISDN or the IMSI with a line identifier in a seconddatabase; removing the first association or the MSISDN from the firstdatabase; storing the MSISDN and a third association of the MSISDN witha second user account in the first database; receiving a Call DetailRecord (CDR) indicating the line identifier; and generating, based atleast in part the second association and receiving the CDR, a billingreport associated with the first user account.
 9. The method of claim 8,wherein the third association is stored less than one day afterreceiving the cancelation request.
 10. The method of claim 8, whereinthe CDR is received from a mediation node storing an association betweenthe line identifier and the MSISDN or the IMSI.
 11. The method of claim8, further comprising: storing a timestamp associated with thecancelation request representing an occurrence of a user accounttermination event; and generating the billing report based at least inpart on the timestamp.
 12. The method of claim 8, wherein the CDRindicates usage information associated with the line identifier, themethod further comprising: storing a timestamp associated with usageinformation; and generating the billing report based at least in part onthe timestamp.
 13. The method of claim 8, further comprising: storing afirst timestamp associated with the cancelation request storing a secondtimestamp associated with the CDR; and determining that the secondtimestamp indicates an earlier time than the first timestamp.
 14. Themethod of claim 8, wherein the billing report comprises at least one ofusage information, rated usage information, a balance, or a locationassociated with the first user account.
 15. A computing devicecomprising: one or more processors; and one or more non-transitorycomputer-readable media storing computer-executable instructions that,when executed, cause the one or more processors to perform operationscomprising: storing, in a first database, i) a Mobile StationInternational Subscriber Directory Number (MSISDN) or an InternationalMobile Subscriber Identity (IMSI) and ii) a first association of theMSISDN or the IMSI with a first user account; receiving a cancelationrequest comprising a cancelation timestamp associated with the MSISDN orthe IMSI; storing a second association of the MSISDN or the IMSI with aline identifier in a second database; removing the first association orthe MSISDN from the first database; storing the MSISDN and a thirdassociation of the MSISDN with a second user account in the firstdatabase; receiving a Call Detail Record (CDR) indicating the lineidentifier; and transmitting, based at least in part the secondassociation and receiving the CDR, data associated with the first useraccount.
 16. The computing device of claim 15, wherein the cancelationtimestamp indicates a time, the time being associated with a firstcancelation of the first user account or a second cancelation of thesecond association.
 17. The computing device of claim 15, wherein thethird association is stored less than one day after receiving thecancelation request.
 18. The computing device of claim 15, wherein theCDR is received from a mediation node storing an association between theline identifier and the MSISDN or the IMSI.
 19. The computing device ofclaim 15, wherein the operations further comprise: storing a timestampassociated with the cancelation request representing an occurrence of auser account termination event; and transmitting the data associatedwith the first user account based at least in part on the timestamp. 20.The computing device of claim 15, wherein the data associated with thefirst user account comprises at least one of usage information, ratedusage information, a balance, or a location associated with the firstuser account.